The IDPS must produce sensor log records containing sufficient information to determine if the event was a success or failure.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-34602	SRG-NET-999999-IDPS-00217	SV-45468r1_rule		Low

Description
Denied traffic must be logged. There may also be some instances where a packet that was permitted or other successful event (i.e., logon) should be logged to establish and correlate the series of events leading up to an outage or attack. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured IDPS.

Description

Denied traffic must be logged. There may also be some instances where a packet that was permitted or other successful event (i.e., logon) should be logged to establish and correlate the series of events leading up to an outage or attack. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured IDPS.

STIG	Date
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide	2012-11-19

Details

Check Text ( C-42817r1_chk )
Examine the aggregated sensor event log on the management console. View entries for several alerts. Verify the events being captured in the sensor logs include the success or failure of the action or request (e.g., login, permission changes) of each event. If the log events do not include the success or failure of the action or request (e.g., login, permission changes), this is a finding.

Fix Text (F-38865r1_fix)
Configure the sensor event log, so entries in the logs include the success or failure of the action or request (e.g., login, permission changes).